The retention core and the decision logic behind it. Every morning the athlete logs a weigh-in; the app turns that into a calm verdict — and, only on confirmed evidence, an offer to change the plan. This map shows the loop, the verdict cascade that judges each reading, and the off-pace branches. The why behind the thresholds is in the Methodology Brief; this is the screen-and-decision flow.
The habit that predicts retention. Four beats, every morning, then back to Today — most days it takes ten seconds.
Each reading steps through three timescales against the cycle-adjusted expected weight. Steps 1–2 are silent — they never flag the athlete. Only the 7-day rate produces the displayed verdict.
Displayed outcomes: On track Behind / Too fast Off the pace — red reserved for genuine risk.
Being off-pace runs on two channels. A soft early-warning that never changes anything, and the hard triggers that actually offer a new plan.
A CUSUM accumulates small same-direction deviations from plan and opens a quiet “I'm watching this” note in ~2–3 days of consistent drift — days before a 7-day rate could confirm it. It never launches a plan change. Tightens its sensitivity as fight day nears. → Screens: Drift-watch · creeping behind / cutting fast
The Change-your-plan flow is offered only on a confirmed, hysteresis-protected hard trigger — never one noisy window:
Drifting behind → tighten intake gently. Cutting too fast → add food back. The flow only ever offers safe routes — move up a division, move the date, or hold at the capped safe rate — and nothing changes until the athlete chooses. The soft drift-watch and the hard triggers map to the matching variants in All Screens.
In the clickable prototype, the Pace toggle (On / Behind / Off) drives these verdicts live across Dashboard, Result and the drift screens, and the logged number on the Log screen now derives its own verdict. The off-pace screens lead to the matching Change-Plan screen: behind → projection, fast → safety.
Companion to OnWeight, Logic & Flows.md (§9 tracking, §9.2 triggers), the Methodology Brief (the evidence), and the Camp Lifecycle map (this loop runs inside the Active state).